Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

For those of you interested in downloading the daily build, I have let
the cat out of the bag today, in which we will have version 2.5.2 in the next coming weeks.

Why the update if we are on schedule for 2.6? Well, these features where left out of 2.5 until I was sure they where ok and now they are.

So what does the update include:

1. Two new interception points: afterHandlerCreation, afterPluginCreation

2. Fixes for using the coldboxproxy with event gateways (Thanks Tom!)

3. API documentation

4. Lightwire updated to include "containsBean" method

5. Due to the popularity of the flash RC persitance via setNextEvent and setNextRoute, the method has been now exposed to the controller and all plugins/handlers/interceptors. You can now persist variables from the collection into the flash RC Ram via the method:

"persistVariables(comma-delimmited list of keys)".

You can now use it to persist on demand. (Thanks Mark!!)

6. One new interceptor: autowire.cfc

This amazing interceptor will autowire your handlers and plugins with beans from the ioc plugin (whether coldspring or lightwire). So you can easily autowire your handlers and plugins with service objects or whatever you want. Man, am I gonna have to configure mooore stuff. Well, not thanks to conventions and metadata. All you do is:

- Declare the 'autowire=true' in your cfcomponent declaration.

- Then just create the getter/setters for your services (*They have to
be the same name as the bean names in your configurations)

And that is IT!!! No configuration, just add the "autowire" metadata parameter
to your handlers and plugins, create the getters and setters and you
are ready to roll.

The interceptor declaration would be:
true

The debugmode property just spits out to the log files any errors or
information stuff.

So there you go, one more surprise coming probably in about a week and
2.5.2 is a go!!

Enjoy the autowire interceptor!!

Add Your Comment

(1)

Jan 16, 2008 21:27:55 UTC

by Tony Garcia

Awesome stuff Luis. You put out cool new features so often, I can't keep up! Looking forward to playing with this stuff. Thanks!

Recent Entries

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.

For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.

Maria Jose Herrera
Maria Jose Herrera
September 18, 2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026